Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
custom01...custom09: Specifies that a customer-specific (custom) dictionary is to be used for expansion and behaviors.
e2standard: Specifies that the E2-Standard-Dictionary is to be used.
Important: If this keyword is not configured, the system defaults to the default dictionary (e2standard). In the Proxy-CSCF configuration, at any time, the location-info dictionary can either be an explicitly configured dictionary or the default dictionary. Hence, there is no corresponding “no” CLI to disable the location-info dictionary setting.
Gq-custom: Specifies that the Gq Operax dictionary is to be used for Operax-specific behavior.
Gq-standard: Specifies that the Gq standard dictionary is to be used.
Rq-custom: Specifies that the Rq custom dictionary is to be used.
Rx-rel8: Specifies that the Rx Release 8 dictionary is to be used.
Rx-standard: Specifies that the Rx standard dictionary is to be used.
Tx-standard: Specifies that the Tx standard dictionary is to be used.
custom01...custom09: Specifies that a customer-specific (custom) dictionary, for customer-specific expansion and behaviors, is to be used.
gq-custom : Specifies that the Gq Operax dictionary is to be used for Operax-specific behavior.
gq-standardd: Specifies that the Gq standard dictionary is to be used.
rq-custom: Specifies that the Rq custom dictionary is to be used.
rx-custom01...rx-custom05: Specifies that a customer-specific (custom) dictionary, for customer-specific expansion and behaviors, is to be used.
rx-rel8: Specifies that the Rx Release 8 dictionary is to be used.
rx-standard: Specifies that the Rx standard dictionary is to be used.
tx-standard: Specifies that the Tx standard dictionary is to be used.
endpoint_name must be the endpoint’s name and an alpha and/or numeric string of 1 through 63 characters in length.
peer_name must be from 1 to 63 alpha and/or numeric characters in length.
Diameter peer servers are configured through the diameter endpoint command in the Context Configuration Mode. The
diameter endpoint command is a generic command and can be found in the Cisco ASR 5000 Series Command Line Interface Reference.
realm_name must be from 1 to 63 alpha and/or numeric characters in length.
peer_name must be from 1 to 63 alpha and/or numeric characters in length.
realm_name must be from 1 to 63 alpha and/or numeric characters in length.
Important: The “
diameter location-info peer-select peer <primary_peer> peer-realm <primary_peer_realm> secondary-peer <secondary_peer> sec-peer-realm <secondary_peer_realm>” CLI configures Peer Switching—selecting which peers the Diameter messages are routed to. When the secondary peer is configured, in case the primary fails, request messages are rerouted to the secondary. Note that the “
no diameter location-info peer-select” CLI command will remove the entire Peer Switching CLI from the configuration.
sec must be an integer from 1 to 300.
Important: If this keyword is not configured, the system defaults to the default setting (10 seconds). In the Proxy-CSCF configuration, at any time, the request-timeout setting can either be an explicitly configured value or the default value. Hence, there is no corresponding “no” CLI to disable the request-timeout setting.
visited-ue: Allow emergency-registration from a visited UE. By default, it's allowed.
3gpp-ims-xml-body: Allow 3GPP IM CN XML body to be added in 380 response messages.
anonymous: Allow anonymous subscribers (unregistered UEs) to initiate emergency sessions.
non-emergency-registered: Allow non-emergency registered subscribers to initiate emergency sessions.
sdp-cs-media: Allow emergency calls with SDP CS Media.
visited-ue: Allow emergency calls from visited UE.
3gpp-cs: Specifies 3GPP CS access preference in header.
3gpp-ims (default): Specifies 3GPP IMS access preference in header.
limit must be an integer from 512 to 65535.
id must be from 1 to 79 alpha and/or numeric characters in length.
ip_address is expressed in standard dotted decimal notation for IPv4 or colon notation for IPv6.
The mcc and
mnc values are compared against those received in p-access-network-info headers as per 3GPP TS 24.229. If
mnc is not provided in the criteria only
mcc is compared.
mandatory: Both inbound and outbound will request reliability.
optional(default): Reliability is imposed by inbound side. Only if inbound call requests reliability will outbound also request reliability.
p-access-network-info: Inserts P-Access-Network-Info (PANI) header in received request/response.
p-cust1-prid-info: Inserts a custom header, P-LGUPlus-PRID-Info, which contains the private user id of the user sending any dialogue creating request or any standalone requests, to be added in the message toward nexthop. Addition of the header will be done when P-CSCF forwards this message.
p-user-database: Inserts P-User-Database (PUD) header in SIP (REGISTER) message and Invite from I-CSCF to S-CSCF.